<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.5"/>
<title>xilnvm: xilnvm_efuse_versal_input.h File Reference</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="navtree.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="resize.js"></script>
<script type="text/javascript" src="navtree.js"></script>
<script type="text/javascript">
  $(document).ready(initResizable);
  $(window).load(resizeHeight);
</script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
<link href="HTML_custom.css" rel="stylesheet" type="text/css"/>
</head>
<body>
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
 <tbody>
 <tr style="height: 56px;">
  <td id="projectlogo"><img alt="Logo" src="xlogo_bg.png"/></td>
  <td style="padding-left: 0.5em;">
   <div id="projectname">xilnvm
   </div>
   <div id="projectbrief">Vitis Drivers API Documentation</div>
  </td>
 </tr>
 </tbody>
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.5 -->
  <div id="navrow1" class="tabs">
    <ul class="tablist">
      <li><a href="index.html"><span>Overview</span></a></li>
      <li><a href="annotated.html"><span>Data&#160;Structures</span></a></li>
      <li><a href="globals.html"><span>APIs</span></a></li>
      <li><a href="files.html"><span>File&#160;List</span></a></li>
    </ul>
  </div>
</div><!-- top -->
<div id="side-nav" class="ui-resizable side-nav-resizable">
  <div id="nav-tree">
    <div id="nav-tree-contents">
      <div id="nav-sync" class="sync"></div>
    </div>
  </div>
  <div id="splitbar" style="-moz-user-select:none;"
       class="ui-resizable-handle">
  </div>
</div>
<script type="text/javascript">
$(document).ready(function(){initNavTree('xilnvm__efuse__versal__input_8h.html','');});
</script>
<div id="doc-content">
<div class="header">
  <div class="summary">
<a href="#define-members">Macros</a>  </div>
  <div class="headertitle">
<div class="title">xilnvm_efuse_versal_input.h File Reference</div>  </div>
</div><!--header-->
<div class="contents">
<a name="details" id="details"></a><h2 class="groupheader">Overview</h2>
<div class="textblock"><p>This file contains macros which needs to configured by user based on the options selected by user operations will be performed.</p>
<dl class="section note"><dt>Note</dt><dd><pre class="fragment">   User configurable parameters for Versal eFUSE
</pre> <hr/>
 #define XNVM_EFUSE_GLITCH_DET_WR_LOCK FALSE TRUE permanently disables writing to ANLG_TRIM_3 row FALSE will not modify the bits in that row in eFUSE</dd></dl>
<p>#define XNVM_EFUSE_GD_HALT_BOOT_EN_1_0 FALSE TRUE permanently enables halt boot in ROM when a glitch observed FALSE will not modify the control bit in eFUSE</p>
<p>#define XNVM_EFUSE_GD_ROM_MONITOR_EN FALSE TRUE permanently enables the glitch monitoring in ROM FALSE will not modify the control bit in eFUSE</p>
<p>#define XNVM_EFUSE_GEN_ERR_HALT_BOOT_EN_1_0 FALSE TRUE halts the boot at ROM stage when any error other than environmental and glitch observed FALSE will not modify the control bit in eFUSE</p>
<p>#define XNVM_EFUSE_ENV_ERR_HALT_BOOT_EN_1_0 FALSE TRUE halts the boot at ROM stage when any environmental error observed FALSE will not modify the control bit in eFUSE</p>
<p>#define XNVM_EFUSE_REG_INIT_DIS FALSE TRUE permanently disables register initialization FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_BOOT_ENV_WR_LK FALSE TRUE will permanently disable the efuse programming and hardware testbit programming on row 37 in EFUSE_0_MAP and hardware testbit programming on row 43 in EFUSE_0_MAP will be disabled as well. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_PMC_SC_EN FALSE TRUE will enable PMC Scan Clear during ROM operation or during lockdown. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_AUTH_JTAG_LOCK_DIS FALSE TRUE will disable the Authenticated JTAG feature after secure lock down. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_AUTH_JTAG_DIS FALSE TRUE will disable the Authenticated JTAG feature. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_JTAG_DIS FALSE TRUE will disable all JTAG instructions. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_JTAG_ERROR_OUT_DIS FALSE TRUE will mask all errors reported in the JTAG ERROR_STATUS instruction and masks the ROM_STATE[3:0] status reported in the JTAG STATUS instruction. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_AES_DIS FALSE TRUE will disable the AES engine. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_PPK0_WR_LK FALSE TRUE permanently disables writing to PPK0 eFuse. FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_PPK1_WR_LK FALSE TRUE permanently disables writing to PPK1 eFuse. FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_PPK2_WR_LK FALSE TRUE permanently disables writing to PPK2 eFuse. FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_AES_CRC_LK FALSE TRUE permanently disables the CRC checks on AES key. FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_AES_WR_LK FALSE TRUE permanently disables writing to AES key FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_USER_KEY_0_CRC_LK FALSE TRUE permanently disables the CRC checks on User 0 key. FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_USER_KEY_0_WR_LK FALSE TRUE permanently disables writing to User 0 key FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_USER_KEY_1_CRC_LK FALSE TRUE permanently disables the CRC checks on User 1 key. FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_USER_KEY_1_WR_LK FALSE TRUE permanently disables writing to User 1 key FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_HWTSTBITS_DIS FALSE TRUE will disable the hardware testbit mode (soft programming of efuse cache) completely. FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_PPK0_INVLD FALSE TRUE invalidates the PPK0 hash stored in eFuses. FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_PPK1_INVLD FALSE TRUE invalidates the PPK1 hash stored in eFuses. FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_PPK2_INVLD FALSE TRUE invalidates the PPK2 hash stored in eFuses. FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_CRYPTO_KAT_EN FALSE TRUE will run KAT on the CRYPTO engines (AES,SHA,RSA) prior to the first time being used. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_LBIST_EN FALSE TRUE will make the firmware to run LBIST when briging up LPD. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_SAFETY_MISSION_EN FALSE TRUE will make the ERROR_OUT pin a different meaning. When the eFUSE cache gets loaded - this pin asserted immediately. The pin goes low when a safety state has been written to the safety state register. This is effectively an external signal to indicate safe state. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_SYSMON_TEMP_EN FALSE TRUE will enable first level architectural temperature check. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_SYSMON_VOLT_EN FALSE TRUE will enable first level architectural voltage check. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_SYSMON_TEMP_HOT FALSE TRUE will burn the boot time temparature upper limit provided in XNVM_EFUSE_SYSMON_TEMP_HOT_FUSES. FALSE will ignore the boot time temparature upper limit provided in XNVM_EFUSE_SYSMON_TEMP_HOT_FUSES.</p>
<p>#define XNVM_EFUSE_SYSMON_VOLT_PMC FALSE TRUE will burn the boot time voltage setting for VCCINT_PMC provided in XNVM_EFUSE_SYSMON_VOLT_PMC_FUSES. FALSE will ignore the boot time voltage setting for VCCINT_PMC provided in XNVM_EFUSE_SYSMON_VOLT_PMC_FUSES.</p>
<p>#define XNVM_EFUSE_SYSMON_VOLT_PSLP FALSE TRUE will burn the boot time voltage setting for VCCINT_PSLP provided in XNVM_EFUSE_SYSMON_VOLT_PSLP_FUSE. FALSE will ignore the boot time voltage setting for VCCINT_PSLP provided in XNVM_EFUSE_SYSMON_VOLT_PSLP_FUSE.</p>
<p>#define XNVM_EFUSE_SYSMON_VOLT_SOC FALSE TRUE will enable boot time voltage monitoring setting to HP voltage level. FALSE will not modify this control bit of efuse. 0x0: MP voltage level 0x1: HP voltage level</p>
<p>#define XNVM_EFUSE_SYSMON_TEMP_COLD FALSE TRUE will burn the boot time temparature lower limit provided in XNVM_EFUSE_SYSMON_TEMP_COLD_FUSES. FALSE will ignore the boot time temparature lower limit provided in XNVM_EFUSE_SYSMON_TEMP_COLD_FUSES.</p>
<p>#define XNVM_EFUSE_LPD_MBIST_EN FALSE TRUE will make the ROM code to run MBIST-clear on the LPD during USB boot mode and the FW will run MBIST-clear on the LPD during all other boot modes. Also checked by FW for secure lock down on the LPD FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_PMC_MBIST_EN FALSE TRUE will make the ROM code to run MBIST-clear on the PMC during all boot modes. Also checked by ROM for secure lockdown. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_LPD_NOC_SC_EN FALSE TRUE will make the ROM code to run SCAN-clear on the LPD during USB boot or on the NOC on a SSIT slave SLR. Also checked by FW for secure lockdown FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_SYSMON_VOLT_MON_EN FALSE TRUE will make the ROM will perform the voltage check specified in the BOOT_ENV_CTRL register. FALSE will not modify this control bit of efuse.</p>
<p>#define XNVM_EFUSE_SYSMON_TEMP_MON_EN FALSE TRUE will make the ROM to perform the temperature check specified in the BOOT_ENV_CTRL register FALSE will not modify this control bit of efuse.</p>
<h2>Following has to be set for programming required keys/data </h2>
<p>#define XNVM_EFUSE_WRITE_GLITCH_CFG FALSE TRUE will burn the glitch configuration data in XNVM_EFUSE_GLITCH_CFG FALSE will ignore the data provided in XNVM_EFUSE_GLITCH_CFG</p>
<p>#define XNVM_EFUSE_WRITE_AES_KEY FALSE TRUE will burn the AES key provided in XNVM_EFUSE_AES_KEY. FALSE will ignore the key provided in XNVM_EFUSE_AES_KEY.</p>
<p>#define XNVM_EFUSE_WRITE_USER_KEY_0 FALSE TRUE will burn the User key 0 provided in XNVM_EFUSE_USER_KEY_0. FALSE will ignore the key provided in XNVM_EFUSE_USER_KEY_0.</p>
<p>#define XNVM_EFUSE_WRITE_USER_KEY_1 FALSE TRUE will burn the User key 1 provided in XNVM_EFUSE_USER_KEY_1. FALSE will ignore the key provided in XNVM_EFUSE_USER_KEY_1.</p>
<p>#define XNVM_EFUSE_WRITE_DEC_EFUSE_ONLY FALSE TRUE will burn the lower 16 bits of Security Misc 0 eFuse row. FALSE will not modify the lower 16 bits of Security Misc 0 eFuse row.</p>
<p>#define XNVM_EFUSE_WRITE_METAHEADER_IV FALSE TRUE will burn the MetaHeader IV provided in XNVM_EFUSE_METAHEADER_IV FALSE will ignore the data provided in XNVM_EFUSE_METAHEADER_IV</p>
<p>#define XNVM_EFUSE_WRITE_BLACK_OBFUS_IV FALSE TRUE will burn Black Obfus IV provided in XNVM_EFUSE_BLACK_OBFUS_IV. FALSE will ignore the data provided in XNVM_EFUSE_BLACK_OBFUS_IV.</p>
<p>#define XNVM_EFUSE_WRITE_PLM_IV FALSE TRUE will burn the Plm IV provided in XNVM_EFUSE_PLM_IV. FALSE will ignore the data provided in XNVM_EFUSE_PLM_IV.</p>
<p>#define XNVM_EFUSE_WRITE_DATA_PARTITION_IV FALSE TRUE will burn the Data Partition IV in XNVM_EFUSE_DATA_PARTITION_IV. FALSE will ignore the data provided in XNVM_EFUSE_DATA_PARTITION_IV.</p>
<p>#define XNVM_EFUSE_WRITE_PPK0_HASH FALSE TRUE will burn PPK0 with it's SHA3 hash provided in XNVM_EFUSE_PPK0_HASH. FALSE will ignore the hash provided in XNVM_EFUSE_PPK0_SHA3_HASH.</p>
<p>#define XNVM_EFUSE_WRITE_PPK1_HASH FALSE TRUE will burn PPK1 with it's SHA3 hash provided in XNVM_EFUSE_PPK1_HASH. FALSE will ignore the hash provided in XNVM_EFUSE_PPK1_HASH.</p>
<p>#define XNVM_EFUSE_WRITE_PPK2_HASH FALSE TRUE will burn PPK2 with it's SHA3 hash provided in XNVM_EFUSE_PPK2_HASH. FALSE will ignore the hash provided in XNVM_EFUSE_PPK2_HASH.</p>
<p>#define XNVM_EFUSE_WRITE_PPK0_SLR1_HASH FALSE TRUE will burn PPK0 in SLR1 with it's SHA3 hash provided in XNVM_EFUSE_PPK0_SLR1_HASH. FALSE will ignore the hash provided in XSK_EFUSEPS_PPK0_SLR1_HASH.</p>
<p>#define XNVM_EFUSE_WRITE_PPK1_SLR1_HASH FALSE TRUE will burn PPK1 in SLR1 with it's SHA3 hash provided in XNVM_EFUSE_PPK1_SLR1_HASH. FALSE will ignore the hash provided in XNVM_EFUSE_PPK1_SLR1_HASH.</p>
<p>#define XNVM_EFUSE_WRITE_PPK2_SLR1_HASH FALSE TRUE will burn PPK2 in SLR1 with it's SHA3 hash provided in XNVM_EFUSE_PPK2_SLR1_HASH. FALSE will ignore the hash provided in XNVM_EFUSEPS_PPK2_SLR1_HASH.</p>
<p>#define XNVM_EFUSE_WRITE_PPK0_SLR2_HASH FALSE TRUE will burn PPK0 in SLR2 with it's SHA3 hash provided in XNVM_EFUSE_PPK0_SLR2_HASH. FALSE will ignore the hash provided in XNVM_EFUSE_PPK0_SLR2_HASH.</p>
<p>#define XNVM_EFUSE_WRITE_PPK1_SLR2_HASH FALSE TRUE will burn PPK1 in SLR2 with it's SHA3 hash provided in XNVM_EFUSE_PPK1_SLR2_HASH. FALSE will ignore the hash provided in XNVM_EFUSE_PPK1_SLR2_HASH.</p>
<p>#define XNVM_EFUSE_WRITE_PPK2_SLR2_HASH FALSE TRUE will burn PPK2 in SLR2 with it's SHA3 hash provided in XNVM_EFUSE_PPK2_SLR2_HASH. FALSE will ignore the hash provided in XNVM_EFUSE_PPK2_SLR2_HASH.</p>
<p>#define XNVM_EFUSE_WRITE_PPK0_SLR3_HASH FALSE TRUE will burn PPK0 in SLR3 with it's SHA3 hash provided in XNVM_EFUSE_PPK0_SLR3_HASH. FALSE will ignore the hash provided in XNVM_EFUSE_PPK0_SLR3_HASH.</p>
<p>#define XNVM_EFUSE_WRITE_PPK1_SLR3_HASH FALSE TRUE will burn PPK1 in SLR3 with it's SHA3 hash provided in XNVM_EFUSE_PPK1_SLR3_HASH. FALSE will ignore the hash provided in XNVM_EFUSE_PPK1_SLR3_HASH.</p>
<p>#define XNVM_EFUSE_WRITE_PPK2_SLR3_HASH FALSE TRUE will burn PPK2 in SLR3 with it's SHA3 hash provided in XNVM_EFUSE_PPK2_SLR3_HASH. FALSE will ignore the hash provided in XNVM_EFUSE_PPK2_SLR3_HASH.</p>
<p>#define XNVM_EFUSE_WRITE_REVOCATION_ID_0 FALSE TRUE will burn Revocation Id 0 eFuse with the data provided in XNVM_EFUSE_REVOCATION_ID_0 FUSES. FALSE will ignore the value provided in XNVM_EFUSE_REVOCATION_ID_0</p>
<p>#define XNVM_EFUSE_WRITE_REVOCATION_ID_1 FALSE TRUE will burn Revocation Id 1 eFuse with the data provided in XNVM_EFUSE_REVOCATION_ID_1 FUSES. FALSE will ignore the value provided in XNVM_EFUSE_REVOCATION_ID_1</p>
<p>#define XNVM_EFUSE_WRITE_REVOCATION_ID_2 FALSE TRUE will burn Revocation Id 2 eFuse with the data provided in XNVM_EFUSE_REVOCATION_ID_2 FUSES. FALSE will ignore the value provided in XNVM_EFUSE_REVOCATION_ID_2.</p>
<p>#define XNVM_EFUSE_WRITE_REVOCATION_ID_3 FALSE TRUE will burn Revocation Id 3 eFuse with the data provided in XNVM_EFUSE_REVOCATION_ID_3 FUSES. FALSE will ignore the value provided in XNVM_EFUSE_REVOCATION_ID_3</p>
<p>#define XNVM_EFUSE_WRITE_REVOCATION_ID_4 FALSE TRUE will burn Revocation Id 4 eFuse with the data provided in XNVM_EFUSE_REVOCATION_ID_4 FUSES. FALSE will ignore the value provided in XNVM_EFUSE_REVOCATION_ID_4</p>
<p>#define XNVM_EFUSE_WRITE_REVOCATION_ID_5 FALSE TRUE will burn Revocation Id 5 eFuse with the data provided in XNVM_EFUSE_REVOCATION_ID_5 FUSES. FALSE will ignore the value provided in XNVM_EFUSE_REVOCATION_ID_5</p>
<p>#define XNVM_EFUSE_WRITE_REVOCATION_ID_6 FALSE TRUE will burn Revocation Id 6 eFuse with the data provided in XNVM_EFUSE_REVOCATION_ID_6 FUSES. FALSE will ignore the value provided in XNVM_EFUSE_REVOCATION_ID_6.</p>
<p>#define XNVM_EFUSE_WRITE_REVOCATION_ID_7 FALSE TRUE will burn Revocation Id 7 eFuse with the data provided in XNVM_EFUSE_REVOCATION_ID_7 FUSES. FALSE will ignore the value provided in XNVM_EFUSE_REVOCATION_ID_7.</p>
<p>#define XNVM_EFUSE_WRITE_USER_FUSES FALSE TRUE will burn User eFuses provided in XNVM_EFUSE_USER_FUSES. FALSE will ignore the value provided in XNVM_EFUSE_USER_FUSES.</p>
<p>#define XNVM_EFUSE_SYSMON_TEMP_HOT_FUSES 0 The value mentioned in this will be used to set the boot time temparature upper limit. Valid values are 0/1/2/3 0: 125C 1: 100C 2: 110C 3: 125C By default the value is 0.</p>
<p>#define XNVM_EFUSE_SYSMON_VOLT_PMC_FUSES 0 The value mentioned in this will be used to set the boot time voltage setting for VCCINT_PMC. Valid values are 0/1/2/3 limit. 0x0: Full range check 0x1: LP voltage level 0x2: MP voltage level 0x3: HP voltage level By default the value is 0.</p>
<p>#define XNVM_EFUSE_SYSMON_VOLT_PSLP_FUSE 0 The value mentioned in this will be used to set the boot time voltage setting for VCCINT_PSLP. Valid values are 0/1/2/3 limit. 0x0: Full range check 0x1: LP voltage level 0x2: MP voltage level 0x3: HP voltage level By default the value is 0.</p>
<p>#define XNVM_EFUSE_SYSMON_TEMP_COLD_FUSES 0 The value mentioned in this will be used to set the boot time temparature lower limit. Valid values are 0/1/2/3 0: -55C 1: 0C 2: -40C 3: -55C By default the value is 0.</p>
<p>Note: To program user eFuses you have to give the start User fuse number to be programmed at XNVM_EFUSE_PRGM_USER_FUSE_NUM and starting with that number of user fuses to be programmed should be mentioned at XNVM_EFUSE_NUM_OF_USER_FUSES. XNVM_EFUSE_USER_FUSES string should be multiples of 8 bytes always. Which means that if the string is 16 bytes, it will program 2 user eFuses. XNVM_EFUSE_PRGM_USER_FUSE_NUM range is 1 to 63.</p>
<p>Example : When XNVM_EFUSE_WRITE_USER_FUSES is TRUE and XNVM_EFUSE_PRGM_USER_FUSE_NUM is 4 - User eFuse number from where to start write. XNVM_EFUSE_NUM_OF_USER_FUSES is 2 - Number of User eFuses to program XNVM_EFUSE_USER_FUSES "1234578ABCDEF58" - User eFuse data to program UserFuse 4 will be programmed with 0x1234578 and UserFuse 5 will be programmed with 0xABCDEF58.</p>
<p>#define XNVM_EFUSE_READ_USER_FUSE_NUM XNVM_EFUSE_PRGM_USER_FUSE_NUM XNVM_EFUSE_READ_USER_FUSE_NUM - User eFuse number from where to start read. By default it reads from XNVM_EFUSE_PRGM_USER_FUSE_NUM</p>
<p>#define XNVM_EFUSE_READ_NUM_OF_USER_FUSES XNVM_EFUSE_NUM_OF_USER_FUSES XNVM_EFUSE_READ_NUM_OF_USER_FUSES - Number of eFuses to be read By default it reads XNVM_EFUSE_NUM_OF_USER_FUSES</p>
<p>#define XNVM_EFUSE_ENV_MONITOR_DISABLE FALSE TRUE will disable the temparature and voltage checks before eFuse programming. FALSE will not disable the temparature and voltage checks before eFuse programming. By default the value will be FALSE.</p>
<p>#define XNVM_EFUSE_GLITCH_CFG "00000000" The value mentioned in this will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long and make sure that bit[31] is zero. Valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn any eFuses. Note that for writing the glitch configuration data, XNVM_EFUSE_WRITE_GLITCH_CFG should be set to TRUE</p>
<p>#define XNVM_EFUSE_AES_KEY "0000000000000000000000000000000000000000000000000000000000000000" The value mentioned in this will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn any eFuses. Note that,for writing the AES Key, XNVM_EFUSE_WRITE_AES_KEY should be set to TRUE. NOTE: This AES key is only red key or gray key. To program black key to eFuse, please use xnvm_puf_registration</p>
<p>#define XNVM_EFUSE_USER_KEY_0 "0000000000000000000000000000000000000000000000000000000000000000" The value mentioned in this will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn any eFuses. Note that,for writing the User Key 0, XNVM_EFUSE_WRITE_USER_KEY_0 should be set to TRUE. NOTE: This AES key is only red key or gray key. To program black key to eFuse, please use xnvm_puf_registration</p>
<p>#define XNVM_EFUSE_USER_KEY_1 "0000000000000000000000000000000000000000000000000000000000000000" The value mentioned in this will be converted to hex buffer and written into the Versal eFUSE array when write API used. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn any eFuses. Note that,for writing the User Key 1, XNVM_EFUSE_WRITE_USER_KEY_1 should be set to TRUE. NOTE: This AES key is only red key or gray key. To program black key to eFuse, please use xnvm_puf_registration.</p>
<p>#define XNVM_EFUSE_PPK0_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFUSE array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK0 hash. Note that,for writing the PPK0 hash, XNVM_EFUSE_WRITE_PPK0_HASH should be set to TRUE.</p>
<p>#define XNVM_EFUSE_PPK1_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK1 hash. Note that,for writing the PPK1 hash, XNVM_EFUSE_WRITE_PPK1_HASH should be set to TRUE.</p>
<p>#define XNVM_EFUSE_PPK2_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK2 hash. Note that,for writing the PPK2 hash, XNVM_EFUSE_WRITE_PPK2_HASH should be set to TRUE.</p>
<p>#define XNVM_EFUSE_PPK0_SLR1_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFUSE array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK0 hash. Note that,for writing the PPK0 hash in SLR1, XNVM_EFUSE_WRITE_PPK0_SLR1_HASH should be set to TRUE.</p>
<p>#define XNVM_EFUSE_PPK1_SLR1_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK1 hash. Note that,for writing the PPK1 hash in SLR1, XNVM_EFUSE_WRITE_PPK1_SLR1_HASH should be set to TRUE.</p>
<p>#define XNVM_EFUSE_PPK2_SLR1_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK2 hash. Note that,for writing the PPK2 hash in SLR1, XNVM_EFUSE_WRITE_PPK2_SLR1_HASH should be set to TRUE.</p>
<p>#define XNVM_EFUSE_PPK0_SLR2_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFUSE array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK0 hash. Note that,for writing the PPK0 hash in SLR2, XNVM_EFUSE_WRITE_PPK0_SLR2_HASH should be set to TRUE.</p>
<p>#define XNVM_EFUSE_PPK1_SLR2_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK1 hash. Note that,for writing the PPK1 hash in SLR2, XNVM_EFUSE_WRITE_PPK1_SLR2_HASH should be set to TRUE.</p>
<p>#define XNVM_EFUSE_PPK2_SLR2_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK2 hash. Note that,for writing the PPK2 hash in SLR2, XNVM_EFUSE_WRITE_PPK2_SLR2_HASH should be set to TRUE.</p>
<p>#define XNVM_EFUSE_PPK0_SLR3_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFUSE array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK0 hash. Note that,for writing the PPK0 hash in SLR3, XNVM_EFUSE_WRITE_PPK0_SLR3_HASH should be set to TRUE.</p>
<p>#define XNVM_EFUSE_PPK1_SLR3_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK1 hash. Note that,for writing the PPK1 hash in SLR3, XNVM_EFUSE_WRITE_PPK1_SLR3_HASH should be set to TRUE.</p>
<p>#define XNVM_EFUSE_PPK2_SLR3_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK2 hash. Note that,for writing the PPK2 hash in SLR3, XNVM_EFUSE_WRITE_PPK2_SLR3_HASH should be set to TRUE.</p>
<p>#define XNVM_EFUSE_META_HEADER_IV "000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 24 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn Metaheader IV. Note that,for writing the Metaheader IV, XNVM_EFUSE_WRITE_METAHEADER_IV should be set to TRUE. While writing Metaheader IV, length should be 24 characters long.</p>
<p>#define XNVM_EFUSE_PLM_IV "000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 24 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn Metaheader IV. Note that,for writing the PLM IV, XNVM_EFUSE_WRITE_PLM_IV should be set to TRUE. While writing Plm IV, length should be 24 characters long.</p>
<p>#define XNVM_EFUSE_BLACK_OBFUS_IV "000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFUSE array. This value should be given in string format. It should be 24 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn Black Obfus IV. Note that,for writing the Black Obfus IV, XNVM_EFUSE_WRITE_BLACK_OBFUS_IV should be set to TRUE. While writing Black Obfus IV, length should be 24 characters long.</p>
<p>#define XNVM_EFUSE_DATA_PARTITION_IV "000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 24 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn Data Partition IV. Note that,for writing the Data Partition IV, XNVM_EFUSE_WRITE_DATA_PARTITION_IV should be set to TRUE. While writing Data Partition IV, length should be 24 characters long.</p>
<p>#define XNVM_EFUSE_REVOCATION_ID_0_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Revocation Id 0 eFuse. Note that,for writing the Revocation Id 0 eFuse, XNVM_EFUSE_WRITE_REVOCATION_ID_0 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_REVOCATION_ID_1_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Revocation Id 1 eFuse. Note that,for writing the Revocation Id 1 eFuse, XNVM_EFUSE_WRITE_REVOCATION_ID_1 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_REVOCATION_ID_2_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFUSE array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn the Revocation Id 2 Fuse. Note that,for writing the Revocation Id 2 Fuse, XNVM_EFUSE_WRITE_REVOCATION_ID_2 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_REVOCATION_ID_3_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Revocation Id 3 eFuse. Note that,for writing the Revocation Id 3 eFuse, XNVM_EFUSE_WRITE_REVOCATION_ID_3 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_REVOCATION_ID_4_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Revocation Id 4 eFuse. Note that,for writing the Revocation Id 4 eFuse, XNVM_EFUSE_WRITE_REVOCATION_ID_4 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_REVOCATION_ID_5_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Revocation Id 5 eFuse. Note that,for writing the Revocation Id 5 eFuse, XNVM_EFUSE_WRITE_REVOCATION_ID_5 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_REVOCATION_ID_6_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Revocation Id 6 eFuse. Note that,for writing the Revocation Id 6 eFuse, XNVM_EFUSE_WRITE_REVOCATION_ID_6 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_REVOCATION_ID_7_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Revocation Id 7 eFuse. Note that,for writing the Revocation Id 7 eFuse, XNVM_EFUSE_WRITE_REVOCATION_ID_7 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_OFFCHIP_REVOKE_ID_0_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn the Offchip_Revoke Id 0 eFuse. Note that,for writing the Offchip_Revoke Id 0 eFuse, XNVM_EFUSE_WRITE_OFFCHIP_REVOKE_ID_0 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_OFFCHIP_REVOKE_ID_1_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Offchip_Revoke Id 1 eFuse. Note that,for writing the Offchip_Revoke Id 1 eFuse, XNVM_EFUSE_WRITE_OFFCHIP_REVOKE_ID_1 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_OFFCHIP_REVOKE_ID_2_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFUSE array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn the Offchip_Revoke Id 2 Fuse. Note that,for writing the Offchip_Revoke Id 2 Fuse, XNVM_EFUSE_WRITE_OFFCHIP_REVOKE_ID_2 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_OFFCHIP_REVOKE_ID_3_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Offchip_Revoke Id 3 eFuse. Note that,for writing the Offchip_Revoke Id 3 eFuse, XNVM_EFUSE_WRITE_OFFCHIP_REVOKE_ID_3 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_OFFCHIP_REVOKE_ID_4_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Offchip_Revoke Id 4 eFuse. Note that,for writing the Offchip_Revoke Id 4 eFuse, XNVM_EFUSE_WRITE_OFFCHIP_REVOKE_ID_4 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_OFFCHIP_REVOKE_ID_5_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Offchip_Revoke Id 5 eFuse. Note that,for writing the Offchip_Revoke Id 5 eFuse, XNVM_EFUSE_WRITE_OFFCHIP_REVOKE_ID_5 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_OFFCHIP_REVOKE_ID_6_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Offchip_Revoke Id 6 eFuse. Note that,for writing the Offchip_Revoke Id 6 eFuse, XNVM_EFUSE_WRITE_OFFCHIP_REVOKE_ID_6 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_OFFCHIP_REVOKE_ID_7_FUSES "00000000" The value will be converted to hex buffer and written into the Versal eFuse array when write API used. This value should be given in string format. It should be 8 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered as invalid string and will not burn Offchip_Revoke Id 7 eFuse. Note that,for writing the Offchip_Revoke Id 7 eFuse, XNVM_EFUSE_WRITE_OFFCHIP_REVOKE_ID_7 should be set to TRUE.</p>
<p>#define XNVM_EFUSE_CHECK_AES_KEY_CRC FALSE Default value is FALSE TRUE will validate AES key stored in eFuse by calculating its CRC and comparing with CRC provided in XNVM_EFUSE_EXPECTED_AES_KEY_CRC. CRC verification is done after programming the key to verify the key is programmed properly or not, if not library error outs the same. NOTE: Please make sure if intention is to check only CRC of the provided key and not programming AES key then do not modify XNVM_EFUSE_WRITE_AES_KEY (TRUE will Program key). This check is only applicable for server mode of eFuse example</p>
<p>#define XNVM_EFUSE_CHECK_USER_KEY_0_CRC FALSE Default value is FALSE TRUE will validate USER_KEY_0 key stored in eFuse by calculating its CRC and comparing with CRC provided in XNVM_EFUSE_EXPECTED_USER_KEY0_CRC. CRC verification is done after programming the key to verify the key is programmed properly or not, if not library error outs the same. NOTE: Please make sure if intention is to check only CRC of the provided key and not programming USER_KEY_0 key then do not modify XNVM_EFUSE_WRITE_USER_KEY_0 (TRUE will Program key). This check is only applicable for server mode of eFuse example</p>
<p>#define XNVM_EFUSE_CHECK_USER_KEY_1_CRC FALSE Default value is FALSE TRUE will validate USER_KEY_1 key stored in eFuse by calculating its CRC and comparing with CRC provided in XNVM_EFUSE_EXPECTED_USER_KEY1_CRC. CRC verification is done after programming AES key to verify the key is programmed properly or not, if not library error outs the same. NOTE: Please make sure if intention is to check only CRC of the provided key and not programming USER_KEY_1 key then do not modify XNVM_EFUSE_WRITE_USER_KEY_1 (TRUE will Program key). This check is only applicable for server mode of eFuse example</p>
<p>#define XNVM_EFUSE_EXPECTED_AES_KEY_CRC XNVM_EFUSE_CRC_AES_ZEROS This is expected crc of the programmed Aes key given in hexa decimal. Default is XNVM_EFUSE_CRC_AES_ZEROS Crc of the zero key</p>
<p>#define XNVM_EFUSE_EXPECTED_USER_KEY0_CRC XNVM_EFUSE_CRC_AES_ZEROS This is expected crc of the programmed user key0 given in hexa decimal. Default is XNVM_EFUSE_CRC_AES_ZEROS Crc of the zero key</p>
<p>#define XNVM_EFUSE_EXPECTED_USER_KEY1_CRC XNVM_EFUSE_CRC_AES_ZEROS This is expected crc of the programmed user key1 given in hexa decimal. Default is XNVM_EFUSE_CRC_AES_ZEROS Crc of the zero key</p>
<p>#define XNVM_EFUSE_PPK3_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK3 hash. Note that,USER_[55:48] are repurposed as PPK3 and for writing the PPK3 hash, XNVM_EFUSE_WRITE_PPK3_HASH should be set to TRUE and XNVM_EN_ADD_PPKS should be defined and PPK0,PPK1,PPK2 should already be programmed..</p>
<p>#define XNVM_EFUSE_PPK4_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK4 hash. Note that,USER_[63:56] are repurposed as PPK4 and for writing the PPK4 hash, XNVM_EFUSE_WRITE_PPK4_HASH should be set to TRUE, XNVM_EN_ADD_PPKS should be defined and PPK0,PPK1,PPK2 should already be programmed.</p>
<p>#define XNVM_EFUSE_PPK3_SLR1_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK3 hash. Note that,USER_[55:48] are repurposed as PPK3 and for writing the PPK3 hash, XNVM_EFUSE_WRITE_PPK3_SLR1_HASH should be set to TRUE and XNVM_EN_ADD_PPKS should be defined and PPK0,PPK1,PPK2 should already be programmed..</p>
<p>#define XNVM_EFUSE_PPK4_SLR1_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK4 hash. Note that,USER_[63:56] are repurposed as PPK4 and for writing the PPK4 hash, XNVM_EFUSE_WRITE_PPK4_SLR1_HASH should be set to TRUE, XNVM_EN_ADD_PPKS should be defined and PPK0,PPK1,PPK2 should already be programmed.</p>
<p>#define XNVM_EFUSE_PPK3_SLR2_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK3 hash. Note that,USER_[55:48] are repurposed as PPK3 and for writing the PPK3 hash, XNVM_EFUSE_WRITE_PPK3_SLR2_HASH should be set to TRUE and XNVM_EN_ADD_PPKS should be defined and PPK0,PPK1,PPK2 should already be programmed..</p>
<p>#define XNVM_EFUSE_PPK4_SLR2_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK4 hash. Note that,USER_[63:56] are repurposed as PPK4 and for writing the PPK4 hash, XNVM_EFUSE_WRITE_PPK4_SLR2_HASH should be set to TRUE, XNVM_EN_ADD_PPKS should be defined and PPK0,PPK1,PPK2 should already be programmed.</p>
<p>#define XNVM_EFUSE_PPK3_SLR3_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK3 hash. Note that,USER_[55:48] are repurposed as PPK3 and for writing the PPK3 hash, XNVM_EFUSE_WRITE_PPK3_SLR3_HASH should be set to TRUE and XNVM_EN_ADD_PPKS should be defined and PPK0,PPK1,PPK2 should already be programmed..</p>
<p>#define XNVM_EFUSE_PPK4_SLR3_HASH "0000000000000000000000000000000000000000000000000000000000000000" The value will be converted to a hex buffer and will be written into the Versal eFuse array. This value should be given in string format. It should be 64 characters long, valid characters are 0-9,a-f,A-F. Any other character is considered invalid and will not burn PPK4 hash. Note that,USER_[63:56] are repurposed as PPK4 and for writing the PPK4 hash, XNVM_EFUSE_WRITE_PPK4_SLR3_HASH should be set to TRUE, XNVM_EN_ADD_PPKS should be defined and PPK0,PPK1,PPK2 should already be programmed.</p>
<p>#define XNVM_EFUSE_ADD_PPK_EN FALSE TRUE permanently enables the additional PPK support FALSE will not modify this control bit of efuse</p>
<p>#define XNVM_EFUSE_PPK3_INVLD FALSE TRUE invalidates the PPK3 hash stored in eFuses. FALSE will not modify this control bit of eFuse.</p>
<p>#define XNVM_EFUSE_PPK4_INVLD FALSE TRUE invalidates the PPK4 hash stored in eFuses. FALSE will not modify this control bit of eFuse. </p>
<pre class="fragment"> NOTE: The PPK hash should be the unmodified hash generated by bootgen.
 Single bit programming is allowed for User eFuses (1 through 63),
 however if the user specifies a value that tries to set a bit that was
 previously programmed to 1 back to 0, program throws an error.
 Even if the bits are already programmed user must pass these already
 programmed bits along with the new bits that need to be programmed.
</pre><pre>
 MODIFICATION HISTORY:</pre><pre> Ver    Who     Date    Changes
</p>
<hr/>
<p>
 2.0   kal    03/02/20 First release to add different configurable options
                       to program different eFuse bits.
       kal    08/04/20 Addressed Security review comments.
 2.1   rpo    06/06/20 Support added to write glitch configuration data.
       rpo    06/08/20 Support added to program eFUSE halt boot bits to stop
                       at ROM stage.
       kal    10/12/20 Address Seurity review comments.
 2.3    kal    01/07/21 Added support to SecurityMisc1, BootEnvCtrl,MiscCtrl
                        and remaining eFuses in SecCtrl eFuse rows programming
                        and reading
        kal    02/20/21 Added new macro for Environmental Monitor Disable
 3.1   skg    12/07/22 Added additional PPKs related macros
 3.3   har    12/04/23 Added support for HWTSTBITS_DIS and PMC_SC_EN efuse bits
 3.5   hj     14/04/25 Added support for unique PPK hash programming for each SLR</pre><pre> </pre> </div><table class="memberdecls">
<tr class="heading"><td colspan="2"><h2 class="groupheader"><a name="define-members"></a>
Macros</h2></td></tr>
<tr class="memitem:ae294ab341c16219d171cb5cdf9e3aca9"><td class="memItemLeft" align="right" valign="top">#define&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="xilnvm__efuse__versal__input_8h.html#ae294ab341c16219d171cb5cdf9e3aca9">XNVM_MAX_SLRS</a>&#160;&#160;&#160;4U</td></tr>
<tr class="memdesc:ae294ab341c16219d171cb5cdf9e3aca9"><td class="mdescLeft">&#160;</td><td class="mdescRight">Following is the define to select if the user wants to program Secure control bits.  <a href="#ae294ab341c16219d171cb5cdf9e3aca9">More...</a><br/></td></tr>
<tr class="separator:ae294ab341c16219d171cb5cdf9e3aca9"><td class="memSeparator" colspan="2">&#160;</td></tr>
<tr class="memitem:a26b35fab663a4364f15423fdca8b7081"><td class="memItemLeft" align="right" valign="top">#define&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="xilnvm__efuse__versal__input_8h.html#a26b35fab663a4364f15423fdca8b7081">XNVM_EFUSE_GD_HALT_BOOT_EN_1_0</a>&#160;&#160;&#160;FALSE</td></tr>
<tr class="memdesc:a26b35fab663a4364f15423fdca8b7081"><td class="mdescLeft">&#160;</td><td class="mdescRight">Following is the define to select if the user wants to program Misc control bits.  <a href="#a26b35fab663a4364f15423fdca8b7081">More...</a><br/></td></tr>
<tr class="separator:a26b35fab663a4364f15423fdca8b7081"><td class="memSeparator" colspan="2">&#160;</td></tr>
<tr class="memitem:a6fb3b938cbea92e9389ac511bde55938"><td class="memItemLeft" align="right" valign="top">#define&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="xilnvm__efuse__versal__input_8h.html#a6fb3b938cbea92e9389ac511bde55938">XNVM_EFUSE_SYSMON_TEMP_EN</a>&#160;&#160;&#160;FALSE</td></tr>
<tr class="memdesc:a6fb3b938cbea92e9389ac511bde55938"><td class="mdescLeft">&#160;</td><td class="mdescRight">Following is the define to select if the user wants to program BootEnvCtrl control bits.  <a href="#a6fb3b938cbea92e9389ac511bde55938">More...</a><br/></td></tr>
<tr class="separator:a6fb3b938cbea92e9389ac511bde55938"><td class="memSeparator" colspan="2">&#160;</td></tr>
<tr class="memitem:a3964cd3e2212d5365077febc68da48ae"><td class="memItemLeft" align="right" valign="top">#define&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="xilnvm__efuse__versal__input_8h.html#a3964cd3e2212d5365077febc68da48ae">XNVM_EFUSE_LPD_MBIST_EN</a>&#160;&#160;&#160;FALSE</td></tr>
<tr class="memdesc:a3964cd3e2212d5365077febc68da48ae"><td class="mdescLeft">&#160;</td><td class="mdescRight">Following is the define to select if the user wants to program SecurityMisc1 control bits.  <a href="#a3964cd3e2212d5365077febc68da48ae">More...</a><br/></td></tr>
<tr class="separator:a3964cd3e2212d5365077febc68da48ae"><td class="memSeparator" colspan="2">&#160;</td></tr>
<tr class="memitem:aa2bff8a52477bf6fd766128c9237cc37"><td class="memItemLeft" align="right" valign="top">#define&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="xilnvm__efuse__versal__input_8h.html#aa2bff8a52477bf6fd766128c9237cc37">XNVM_EFUSE_GLITCH_DET_WR_LK</a>&#160;&#160;&#160;FALSE</td></tr>
<tr class="memdesc:aa2bff8a52477bf6fd766128c9237cc37"><td class="mdescLeft">&#160;</td><td class="mdescRight">Following define is to lock the glitch detection row (ANLG_TRIM_3[31])  <a href="#aa2bff8a52477bf6fd766128c9237cc37">More...</a><br/></td></tr>
<tr class="separator:aa2bff8a52477bf6fd766128c9237cc37"><td class="memSeparator" colspan="2">&#160;</td></tr>
<tr class="memitem:afa8ae9a40748e467407c563e03603092"><td class="memItemLeft" align="right" valign="top">#define&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="xilnvm__efuse__versal__input_8h.html#afa8ae9a40748e467407c563e03603092">XNVM_EFUSE_WRITE_GLITCH_CFG</a>&#160;&#160;&#160;FALSE</td></tr>
<tr class="memdesc:afa8ae9a40748e467407c563e03603092"><td class="mdescLeft">&#160;</td><td class="mdescRight">Following is the define to select if the user wants to select Glitch configuration, AES key, User Fuses, PPK0/PPK1/PPK2 hash, IVs, Revocation IDs and IVs.  <a href="#afa8ae9a40748e467407c563e03603092">More...</a><br/></td></tr>
<tr class="separator:afa8ae9a40748e467407c563e03603092"><td class="memSeparator" colspan="2">&#160;</td></tr>
<tr class="memitem:a6d9d6f02bb9056511f8d9cf530f20bef"><td class="memItemLeft" align="right" valign="top">#define&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="xilnvm__efuse__versal__input_8h.html#a6d9d6f02bb9056511f8d9cf530f20bef">XNVM_EFUSE_GLITCH_CFG</a>&#160;&#160;&#160;&quot;00000000&quot;</td></tr>
<tr class="memdesc:a6d9d6f02bb9056511f8d9cf530f20bef"><td class="mdescLeft">&#160;</td><td class="mdescRight">Following defines should be given in the form of hex string.  <a href="#a6d9d6f02bb9056511f8d9cf530f20bef">More...</a><br/></td></tr>
<tr class="separator:a6d9d6f02bb9056511f8d9cf530f20bef"><td class="memSeparator" colspan="2">&#160;</td></tr>
<tr class="memitem:a78d30f09b61d55d9511734b7c9f32c98"><td class="memItemLeft" align="right" valign="top">#define&#160;</td><td class="memItemRight" valign="bottom"><a class="el" href="xilnvm__efuse__versal__input_8h.html#a78d30f09b61d55d9511734b7c9f32c98">XNVM_EFUSE_PRGM_USER_FUSE_NUM</a>&#160;&#160;&#160;0U</td></tr>
<tr class="memdesc:a78d30f09b61d55d9511734b7c9f32c98"><td class="mdescLeft">&#160;</td><td class="mdescRight">Following is the define to select if the user wants to program additional PPK bits.  <a href="#a78d30f09b61d55d9511734b7c9f32c98">More...</a><br/></td></tr>
<tr class="separator:a78d30f09b61d55d9511734b7c9f32c98"><td class="memSeparator" colspan="2">&#160;</td></tr>
</table>
<h2 class="groupheader">Macro Definition Documentation</h2>
<a class="anchor" id="a26b35fab663a4364f15423fdca8b7081"></a>
<div class="memitem">
<div class="memproto">
      <table class="memname">
        <tr>
          <td class="memname">#define XNVM_EFUSE_GD_HALT_BOOT_EN_1_0&#160;&#160;&#160;FALSE</td>
        </tr>
      </table>
</div><div class="memdoc">

<p>Following is the define to select if the user wants to program Misc control bits. </p>

</div>
</div>
<a class="anchor" id="a6d9d6f02bb9056511f8d9cf530f20bef"></a>
<div class="memitem">
<div class="memproto">
      <table class="memname">
        <tr>
          <td class="memname">#define XNVM_EFUSE_GLITCH_CFG&#160;&#160;&#160;&quot;00000000&quot;</td>
        </tr>
      </table>
</div><div class="memdoc">

<p>Following defines should be given in the form of hex string. </p>
<p>The length of AES_KEY string must be 64, PPK hash should be 64 for and for USER_FUSES. </p>

</div>
</div>
<a class="anchor" id="aa2bff8a52477bf6fd766128c9237cc37"></a>
<div class="memitem">
<div class="memproto">
      <table class="memname">
        <tr>
          <td class="memname">#define XNVM_EFUSE_GLITCH_DET_WR_LK&#160;&#160;&#160;FALSE</td>
        </tr>
      </table>
</div><div class="memdoc">

<p>Following define is to lock the glitch detection row (ANLG_TRIM_3[31]) </p>

</div>
</div>
<a class="anchor" id="a3964cd3e2212d5365077febc68da48ae"></a>
<div class="memitem">
<div class="memproto">
      <table class="memname">
        <tr>
          <td class="memname">#define XNVM_EFUSE_LPD_MBIST_EN&#160;&#160;&#160;FALSE</td>
        </tr>
      </table>
</div><div class="memdoc">

<p>Following is the define to select if the user wants to program SecurityMisc1 control bits. </p>

</div>
</div>
<a class="anchor" id="a78d30f09b61d55d9511734b7c9f32c98"></a>
<div class="memitem">
<div class="memproto">
      <table class="memname">
        <tr>
          <td class="memname">#define XNVM_EFUSE_PRGM_USER_FUSE_NUM&#160;&#160;&#160;0U</td>
        </tr>
      </table>
</div><div class="memdoc">

<p>Following is the define to select if the user wants to program additional PPK bits. </p>

</div>
</div>
<a class="anchor" id="a6fb3b938cbea92e9389ac511bde55938"></a>
<div class="memitem">
<div class="memproto">
      <table class="memname">
        <tr>
          <td class="memname">#define XNVM_EFUSE_SYSMON_TEMP_EN&#160;&#160;&#160;FALSE</td>
        </tr>
      </table>
</div><div class="memdoc">

<p>Following is the define to select if the user wants to program BootEnvCtrl control bits. </p>

</div>
</div>
<a class="anchor" id="afa8ae9a40748e467407c563e03603092"></a>
<div class="memitem">
<div class="memproto">
      <table class="memname">
        <tr>
          <td class="memname">#define XNVM_EFUSE_WRITE_GLITCH_CFG&#160;&#160;&#160;FALSE</td>
        </tr>
      </table>
</div><div class="memdoc">

<p>Following is the define to select if the user wants to select Glitch configuration, AES key, User Fuses, PPK0/PPK1/PPK2 hash, IVs, Revocation IDs and IVs. </p>

</div>
</div>
<a class="anchor" id="ae294ab341c16219d171cb5cdf9e3aca9"></a>
<div class="memitem">
<div class="memproto">
      <table class="memname">
        <tr>
          <td class="memname">#define XNVM_MAX_SLRS&#160;&#160;&#160;4U</td>
        </tr>
      </table>
</div><div class="memdoc">

<p>Following is the define to select if the user wants to program Secure control bits. </p>

</div>
</div>
</div><!-- contents -->
</div><!-- doc-content -->
<div id="nav-path" class="navpath"><!-- id is needed for treeview function! -->
	<p class="footer">&copy; Copyright 2015-2022 Xilinx, Inc. All Rights Reserved.</p>
	<p class="footer">&copy; Copyright 2022-2023 Advanced Micro Devices, Inc. All Rights Reserved.</p>
</div>
</body>
</html>
